Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46f4f879c1f0b731f9f51c7896693d3fb84c58871292cba4e727a5244602901c

Tx prefix hash: ee5e684d740646735ea87e2c99c9d6863af3049c94570a9f563597125d155122
Tx public key: 473768ebcb1c9be79afd811b0a7262c656753189ea7f72e81d08559420b47e19
Timestamp: 1700351136 Timestamp [UCT]: 2023-11-18 23:45:36 Age [y:d:h:m:s]: 01:139:04:11:02
Block: 894654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360641 RingCT/type: yes/0
Extra: 01473768ebcb1c9be79afd811b0a7262c656753189ea7f72e81d08559420b47e19021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.666254109000 dcy

stealth address amount amount idx
00: 39067ebebb6f151a0cd83d66895f7b2e184c47b63e0c46aa2d7f72062fade093 0.666254109000 1350861 of 0

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": 894664, "vin": [ { "gen": { "height": 894654 } } ], "vout": [ { "amount": 666254109, "target": { "key": "39067ebebb6f151a0cd83d66895f7b2e184c47b63e0c46aa2d7f72062fade093" } } ], "extra": [ 1, 71, 55, 104, 235, 203, 28, 155, 231, 154, 253, 129, 27, 10, 114, 98, 198, 86, 117, 49, 137, 234, 127, 114, 232, 29, 8, 85, 148, 32, 180, 126, 25, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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