Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849874da45446c96825cc72c849935f9d999c07fa2a87fb3e2e17db107b93f9c

Tx prefix hash: 38f82296ba9aaf40a623bdc0e5395c14a439bc21d9af371e6273c7382e831371
Tx public key: 4b4893a314ab3c1ef3d3db8f5f59b935592b0f8288f16b75f991fec2b23b9db1
Timestamp: 1736039208 Timestamp [UCT]: 2025-01-05 01:06:48 Age [y:d:h:m:s]: 00:162:17:37:22
Block: 1190398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116027 RingCT/type: yes/0
Extra: 014b4893a314ab3c1ef3d3db8f5f59b935592b0f8288f16b75f991fec2b23b9db1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 296fcb0d1e8f92de52655ceff5f2915c4190ba107532459700b3989ebd660dfd 0.600000000000 1676913 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": 1190408, "vin": [ { "gen": { "height": 1190398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "296fcb0d1e8f92de52655ceff5f2915c4190ba107532459700b3989ebd660dfd" } } ], "extra": [ 1, 75, 72, 147, 163, 20, 171, 60, 30, 243, 211, 219, 143, 95, 89, 185, 53, 89, 43, 15, 130, 136, 241, 107, 117, 249, 145, 254, 194, 178, 59, 157, 177, 2, 17, 0, 0, 0, 2, 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