Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e63040e939865a21b2a37a1b8b44e79ab0bc9ebe1727faf71f2162dac76be11

Tx prefix hash: 6ccfc940dbaf18994e901c4384ebf85bfaa4b0a8577f414b544c2390b720a972
Tx public key: 26cdd5c31fd7e562eaf8dc37bd9eb3163061617c43afe935fc368ee508cfdfe3
Timestamp: 1697056748 Timestamp [UCT]: 2023-10-11 20:39:08 Age [y:d:h:m:s]: 01:243:08:04:37
Block: 867548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434975 RingCT/type: yes/0
Extra: 0126cdd5c31fd7e562eaf8dc37bd9eb3163061617c43afe935fc368ee508cfdfe30211000000104b8f5122000000000000000000

1 output(s) for total of 0.819319650000 dcy

stealth address amount amount idx
00: 40bf7364f47c8339493edf5a697fb68f07ef47f956eb17d5e1ff3e9de031ac47 0.819319650000 1322240 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": 867558, "vin": [ { "gen": { "height": 867548 } } ], "vout": [ { "amount": 819319650, "target": { "key": "40bf7364f47c8339493edf5a697fb68f07ef47f956eb17d5e1ff3e9de031ac47" } } ], "extra": [ 1, 38, 205, 213, 195, 31, 215, 229, 98, 234, 248, 220, 55, 189, 158, 179, 22, 48, 97, 97, 124, 67, 175, 233, 53, 252, 54, 142, 229, 8, 207, 223, 227, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 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