Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c52c767b32047c2a810f5d22dad3b8a7be7f66541912a1460f24bb0b10017f3c

Tx prefix hash: e3d87b6f0cecba17ff8a937766158800b185e3ab3a1d1d2ce5edf66c74e0ab71
Tx public key: ad418d7684e870493b497dfb47a907754a6552ac1042d38b001b216bccaa95f6
Timestamp: 1722536955 Timestamp [UCT]: 2024-08-01 18:29:15 Age [y:d:h:m:s]: 00:247:13:16:17
Block: 1078580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176838 RingCT/type: yes/0
Extra: 01ad418d7684e870493b497dfb47a907754a6552ac1042d38b001b216bccaa95f6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd03422cb3694d916442810bc8f11d654e2d560f184f2ae5295356f9da4687d 0.600000000000 1551177 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1078590, "vin": [ { "gen": { "height": 1078580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd03422cb3694d916442810bc8f11d654e2d560f184f2ae5295356f9da4687d" } } ], "extra": [ 1, 173, 65, 141, 118, 132, 232, 112, 73, 59, 73, 125, 251, 71, 169, 7, 117, 74, 101, 82, 172, 16, 66, 211, 139, 0, 27, 33, 107, 204, 170, 149, 246, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8