Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19bbeab8df12c4b7b2ea5ba7b3d030ef299cc4ede68e9db27e2f9502167594f

Tx prefix hash: 9c0e5e65e34ad108f52356a97d375a2d2a8c7c804a26d68598b1b4797e975748
Tx public key: 8cd976c2d862d26c4d0bb091afe5d0638fc9557815c1b16707c9409f1406b358
Timestamp: 1744584920 Timestamp [UCT]: 2025-04-13 22:55:20 Age [y:d:h:m:s]: 00:260:23:35:37
Block: 1260890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184285 RingCT/type: yes/0
Extra: 018cd976c2d862d26c4d0bb091afe5d0638fc9557815c1b16707c9409f1406b3580211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5844043cd17abe8d1c214c6f0732c174b42d16ca4fa41f36fce9a367d07995 0.600000000000 1748055 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": 1260900, "vin": [ { "gen": { "height": 1260890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5844043cd17abe8d1c214c6f0732c174b42d16ca4fa41f36fce9a367d07995" } } ], "extra": [ 1, 140, 217, 118, 194, 216, 98, 210, 108, 77, 11, 176, 145, 175, 229, 208, 99, 143, 201, 85, 120, 21, 193, 177, 103, 7, 201, 64, 159, 20, 6, 179, 88, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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