Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ba109901a6e24dee78af65233029480660509c26cc0f1c137638ce2ff6b0c6

Tx prefix hash: 886fe28a8b56f8b23184649411c547988b0879dd50446f7935fe6c6b41d4895b
Tx public key: 0a21dc68a39e43a9eb816828e3d0e27346096fbf08b3c4aa0f8d246eab0b6853
Timestamp: 1739684898 Timestamp [UCT]: 2025-02-16 05:48:18 Age [y:d:h:m:s]: 00:278:10:06:58
Block: 1220283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196760 RingCT/type: yes/0
Extra: 010a21dc68a39e43a9eb816828e3d0e27346096fbf08b3c4aa0f8d246eab0b6853021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d053ad15c32b0bd7caa1a32b93057071a0fdb914b5965295d5eca1b0fa7e9051 0.600000000000 1707120 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": 1220293, "vin": [ { "gen": { "height": 1220283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d053ad15c32b0bd7caa1a32b93057071a0fdb914b5965295d5eca1b0fa7e9051" } } ], "extra": [ 1, 10, 33, 220, 104, 163, 158, 67, 169, 235, 129, 104, 40, 227, 208, 226, 115, 70, 9, 111, 191, 8, 179, 196, 170, 15, 141, 36, 110, 171, 11, 104, 83, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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