Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2bfd313edfd0418b08e3affa1375fd225a9ed13156dd5c3a4e5ad42305fecd7

Tx prefix hash: aa0a5f87946d29a2229f907a4bcade6f54c35dfc861735cf701be55c158d8c39
Tx public key: 72d6189ef1851288aae46cb3a2dc135ee529c240dc0ff80beba91f0be59e23b5
Timestamp: 1734760305 Timestamp [UCT]: 2024-12-21 05:51:45 Age [y:d:h:m:s]: 00:019:09:04:06
Block: 1179838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13828 RingCT/type: yes/0
Extra: 0172d6189ef1851288aae46cb3a2dc135ee529c240dc0ff80beba91f0be59e23b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56216fdcecc6b3a3a15a8e193fca3e11ab413d35ca88b971218c1be6e98beba1 0.600000000000 1666237 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": 1179848, "vin": [ { "gen": { "height": 1179838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56216fdcecc6b3a3a15a8e193fca3e11ab413d35ca88b971218c1be6e98beba1" } } ], "extra": [ 1, 114, 214, 24, 158, 241, 133, 18, 136, 170, 228, 108, 179, 162, 220, 19, 94, 229, 41, 194, 64, 220, 15, 248, 11, 235, 169, 31, 11, 229, 158, 35, 181, 2, 17, 0, 0, 0, 3, 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