Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a73a1c3f505a1739027a76beee79158a9cb9c4fc35186b9f83315b124db60e4a

Tx prefix hash: 5ac9272b1d16541e5154ba7b14ade04307a93e70a9dd6f7d6f94c3178d5eeb59
Tx public key: 09474ae897fd5b5ff7f66fc80bafe09c624f9834547d9831002cda9c84c26ae0
Timestamp: 1705164958 Timestamp [UCT]: 2024-01-13 16:55:58 Age [y:d:h:m:s]: 01:024:00:45:26
Block: 934550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278247 RingCT/type: yes/0
Extra: 0109474ae897fd5b5ff7f66fc80bafe09c624f9834547d9831002cda9c84c26ae002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a8d29650b19e240b992dbf2dcaa732c49741e14f3253befd0f5362682099e9 0.600000000000 1392564 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": 934560, "vin": [ { "gen": { "height": 934550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a8d29650b19e240b992dbf2dcaa732c49741e14f3253befd0f5362682099e9" } } ], "extra": [ 1, 9, 71, 74, 232, 151, 253, 91, 95, 247, 246, 111, 200, 11, 175, 224, 156, 98, 79, 152, 52, 84, 125, 152, 49, 0, 44, 218, 156, 132, 194, 106, 224, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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