Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 728765ccffd302bb8f22cc151122d09314a49d1d658e72a04b096736e1a5d719

Tx prefix hash: 454e4d47d6221ba25266131f5208d6c70d0b7fc96991a3041d16bd95d2381b7d
Tx public key: 3a441a84a7fb7a6522aea834dbb38260b3ead725ca82b1550a36633985b2aaab
Timestamp: 1648585688 Timestamp [UCT]: 2022-03-29 20:28:08 Age [y:d:h:m:s]: 02:246:08:05:22
Block: 469122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695626 RingCT/type: yes/0
Extra: 013a441a84a7fb7a6522aea834dbb38260b3ead725ca82b1550a36633985b2aaab02110000000437cb3088000000000000000000

1 output(s) for total of 17.123964663000 dcy

stealth address amount amount idx
00: dd6bb97eecafe1749d49a460a1ef518d0f85d4b2e3f98dbc9f2cf4f46ce9e44d 17.123964663000 887994 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": 469132, "vin": [ { "gen": { "height": 469122 } } ], "vout": [ { "amount": 17123964663, "target": { "key": "dd6bb97eecafe1749d49a460a1ef518d0f85d4b2e3f98dbc9f2cf4f46ce9e44d" } } ], "extra": [ 1, 58, 68, 26, 132, 167, 251, 122, 101, 34, 174, 168, 52, 219, 179, 130, 96, 179, 234, 215, 37, 202, 130, 177, 85, 10, 54, 99, 57, 133, 178, 170, 171, 2, 17, 0, 0, 0, 4, 55, 203, 48, 136, 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