Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74a96a1572ace9264cbbea42adc739c8c8f85854dfcf9fe7cfb52b6becd37855

Tx prefix hash: 6594b8398424bdf810bd0db1601a131d3e0fc469dbf2d0607de4636c5609937d
Tx public key: a4cf0d3b9051a5bb89b08a5eb54678e5b8aee638095407b5f6099f0c0b718723
Timestamp: 1702863064 Timestamp [UCT]: 2023-12-18 01:31:04 Age [y:d:h:m:s]: 01:328:00:54:32
Block: 915477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493300 RingCT/type: yes/0
Extra: 01a4cf0d3b9051a5bb89b08a5eb54678e5b8aee638095407b5f6099f0c0b71872302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27123b6d7910ced6db271081c302401d2ec16dd2462e24c63533e505c2da43b 0.600000000000 1372873 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": 915487, "vin": [ { "gen": { "height": 915477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27123b6d7910ced6db271081c302401d2ec16dd2462e24c63533e505c2da43b" } } ], "extra": [ 1, 164, 207, 13, 59, 144, 81, 165, 187, 137, 176, 138, 94, 181, 70, 120, 229, 184, 174, 230, 56, 9, 84, 7, 181, 246, 9, 159, 12, 11, 113, 135, 35, 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