Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 157ea8eb88d628d194c358f3ec7199d35fe93c1cb30ab25841d55fff2021feb6

Tx prefix hash: 9bbfdd20b9bc60f7990091b56ea1d5e52eb7d736dc18de0e329b8fb739afdb08
Tx public key: 6ff44f815399937c1ff77ce473b2c6dc23cb6ee66a566141ed44323edfa5b51a
Timestamp: 1731498847 Timestamp [UCT]: 2024-11-13 11:54:07 Age [y:d:h:m:s]: 00:163:14:35:33
Block: 1152799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116755 RingCT/type: yes/0
Extra: 016ff44f815399937c1ff77ce473b2c6dc23cb6ee66a566141ed44323edfa5b51a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fc68ad90b67d0f0ffa19d34b0bd62793a22a96e4c79c2e87a0f02a6c70b0818 0.600000000000 1638402 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": 1152809, "vin": [ { "gen": { "height": 1152799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fc68ad90b67d0f0ffa19d34b0bd62793a22a96e4c79c2e87a0f02a6c70b0818" } } ], "extra": [ 1, 111, 244, 79, 129, 83, 153, 147, 124, 31, 247, 124, 228, 115, 178, 198, 220, 35, 203, 110, 230, 106, 86, 97, 65, 237, 68, 50, 62, 223, 165, 181, 26, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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