Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aab130a8c1e941b9bd4f2eddad29488546b03405fe0036b4221b49069c6b7a6f

Tx prefix hash: 537f59c21dfa68464325683549b0cfd61b8c908df7c2b2a88849afe88b1f1c87
Tx public key: 92dc3d35d41548c4d85d2238b87afef0367041861f4a713a87be8d2cab4e6d2b
Timestamp: 1711314285 Timestamp [UCT]: 2024-03-24 21:04:45 Age [y:d:h:m:s]: 00:291:21:25:39
Block: 985570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208919 RingCT/type: yes/0
Extra: 0192dc3d35d41548c4d85d2238b87afef0367041861f4a713a87be8d2cab4e6d2b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c828311cb7e5d2f5f2456bc067c8ecf865a325ff1fe737fb227627c2dae95f98 0.600000000000 1445787 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": 985580, "vin": [ { "gen": { "height": 985570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c828311cb7e5d2f5f2456bc067c8ecf865a325ff1fe737fb227627c2dae95f98" } } ], "extra": [ 1, 146, 220, 61, 53, 212, 21, 72, 196, 216, 93, 34, 56, 184, 122, 254, 240, 54, 112, 65, 134, 31, 74, 113, 58, 135, 190, 141, 44, 171, 78, 109, 43, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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