Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1045a9f9155f3a7617eee71705884015d37b274372e1c6373e1da0e731d26947

Tx prefix hash: f2af1a134963a347dfe45d49986b630dbc99315c6e4c24a29b6d0449cce12ee0
Tx public key: 7d0da3a9641f42c2fd9a9ebd1f37171caf0b1bf0c13e9a3bcf9a37a6ac510ef8
Timestamp: 1714440679 Timestamp [UCT]: 2024-04-30 01:31:19 Age [y:d:h:m:s]: 00:214:15:06:00
Block: 1011462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153646 RingCT/type: yes/0
Extra: 017d0da3a9641f42c2fd9a9ebd1f37171caf0b1bf0c13e9a3bcf9a37a6ac510ef80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a38198e176fed059e1af635cc79f748ecb116292a40312fda423c32eb0243d9 0.600000000000 1473700 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": 1011472, "vin": [ { "gen": { "height": 1011462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a38198e176fed059e1af635cc79f748ecb116292a40312fda423c32eb0243d9" } } ], "extra": [ 1, 125, 13, 163, 169, 100, 31, 66, 194, 253, 154, 158, 189, 31, 55, 23, 28, 175, 11, 27, 240, 193, 62, 154, 59, 207, 154, 55, 166, 172, 81, 14, 248, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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