Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 329dfd048de8fd71b21728b9aa7b47f5cb99e8cbd2feaed42ab1a57bc377b1a9

Tx prefix hash: 4ac6a665052798c5a27cc0ccef8d365251d2bab9b5434bbb703b8d465e21d84f
Tx public key: 2f48e0cdc87bf5744af8e7646004a9a4bbc17977450354c7e0c8c005764f50ce
Timestamp: 1713854696 Timestamp [UCT]: 2024-04-23 06:44:56 Age [y:d:h:m:s]: 01:223:19:19:51
Block: 1006613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418629 RingCT/type: yes/0
Extra: 012f48e0cdc87bf5744af8e7646004a9a4bbc17977450354c7e0c8c005764f50ce0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9290bdfa99a7ee6fca40e3571168040c5f9cde18a162be549b0582fdad95eb55 0.600000000000 1467691 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": 1006623, "vin": [ { "gen": { "height": 1006613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9290bdfa99a7ee6fca40e3571168040c5f9cde18a162be549b0582fdad95eb55" } } ], "extra": [ 1, 47, 72, 224, 205, 200, 123, 245, 116, 74, 248, 231, 100, 96, 4, 169, 164, 187, 193, 121, 119, 69, 3, 84, 199, 224, 200, 192, 5, 118, 79, 80, 206, 2, 17, 0, 0, 0, 6, 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