Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383668966d4b33bd4a003de2e8a6c76ec0e31ad80ef8a38698ccd79fae99a5f0

Tx prefix hash: 273ffc6c4c554c8c8fb31bf095c4b1c4418167d8ccd02cdcd620564743fa5c41
Tx public key: d3c6a621a6639dcef91a9acf2217d3a20805737cba7b5cadc2852ce654abdcf9
Timestamp: 1717453486 Timestamp [UCT]: 2024-06-03 22:24:46 Age [y:d:h:m:s]: 00:300:07:53:49
Block: 1036451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214622 RingCT/type: yes/0
Extra: 01d3c6a621a6639dcef91a9acf2217d3a20805737cba7b5cadc2852ce654abdcf90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed0f189eb2e43e7774e01bd2e6ecf706620c6d38a979054a27f2293e4655fe85 0.600000000000 1504978 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": 1036461, "vin": [ { "gen": { "height": 1036451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed0f189eb2e43e7774e01bd2e6ecf706620c6d38a979054a27f2293e4655fe85" } } ], "extra": [ 1, 211, 198, 166, 33, 166, 99, 157, 206, 249, 26, 154, 207, 34, 23, 211, 162, 8, 5, 115, 124, 186, 123, 92, 173, 194, 133, 44, 230, 84, 171, 220, 249, 2, 17, 0, 0, 0, 1, 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