Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0838052a65062ca1dd1c6c4e815634c9c7c8f79c4e134fd6869e078e0546785

Tx prefix hash: f00e3a5f61a09a034d273f0cd812ac901c63212f93df2f480b1e82262e7de37c
Tx public key: 3d72f3cf4cc3c60e39d805640973a5ff42c96e20e77edc51f986a3c52168af88
Timestamp: 1702379918 Timestamp [UCT]: 2023-12-12 11:18:38 Age [y:d:h:m:s]: 01:028:15:32:36
Block: 911494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281817 RingCT/type: yes/0
Extra: 013d72f3cf4cc3c60e39d805640973a5ff42c96e20e77edc51f986a3c52168af8802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac89e3fe58b1338958d4cce207d29e36c568aa31615b586c9c6310600a3073a 0.600000000000 1368698 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": 911504, "vin": [ { "gen": { "height": 911494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac89e3fe58b1338958d4cce207d29e36c568aa31615b586c9c6310600a3073a" } } ], "extra": [ 1, 61, 114, 243, 207, 76, 195, 198, 14, 57, 216, 5, 100, 9, 115, 165, 255, 66, 201, 110, 32, 231, 126, 220, 81, 249, 134, 163, 197, 33, 104, 175, 136, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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