Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b6cf2d3d985feed2932c73e159a948056fccf6eaa7dbf36fe98bc51ddc836a

Tx prefix hash: caadce7c20a0a252b8198c081916552bc5c35692df33965566f7ceeea141aef2
Tx public key: f2dfa4e99cfb7058d08d9da9e19ba52cbb16c8d7d22fc7b7bd799e124e114f8a
Timestamp: 1740817002 Timestamp [UCT]: 2025-03-01 08:16:42 Age [y:d:h:m:s]: 00:056:13:59:37
Block: 1229674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40484 RingCT/type: yes/0
Extra: 01f2dfa4e99cfb7058d08d9da9e19ba52cbb16c8d7d22fc7b7bd799e124e114f8a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 178ef43dc5b713d3bc943e2649b41d942e5cd268f1cda3f52f11c162289d5bcd 0.600000000000 1716561 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": 1229684, "vin": [ { "gen": { "height": 1229674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "178ef43dc5b713d3bc943e2649b41d942e5cd268f1cda3f52f11c162289d5bcd" } } ], "extra": [ 1, 242, 223, 164, 233, 156, 251, 112, 88, 208, 141, 157, 169, 225, 155, 165, 44, 187, 22, 200, 215, 210, 47, 199, 183, 189, 121, 158, 18, 78, 17, 79, 138, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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