Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0e71aa851f3de50146dec96e6bf86affa6b1358485bc801e618486b1f5d781

Tx prefix hash: 7f1540a0740635b184d326c4de0d0550ed839af53b576ce9d5f0f8d214e8fa48
Tx public key: 26e0417a80fd6dc23703764b91e1ce4053eba411aaa66669ccaf56f8604d40b1
Timestamp: 1711545417 Timestamp [UCT]: 2024-03-27 13:16:57 Age [y:d:h:m:s]: 00:298:08:32:33
Block: 987486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213500 RingCT/type: yes/0
Extra: 0126e0417a80fd6dc23703764b91e1ce4053eba411aaa66669ccaf56f8604d40b10211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb368622a33a0c21d2ed756975d7b8f97ae6ea857ebe8fd5d973157575f5e3c1 0.600000000000 1447737 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": 987496, "vin": [ { "gen": { "height": 987486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb368622a33a0c21d2ed756975d7b8f97ae6ea857ebe8fd5d973157575f5e3c1" } } ], "extra": [ 1, 38, 224, 65, 122, 128, 253, 109, 194, 55, 3, 118, 75, 145, 225, 206, 64, 83, 235, 164, 17, 170, 166, 102, 105, 204, 175, 86, 248, 96, 77, 64, 177, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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