Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ffe881d20837bf0483b19c8c6d348d0ef0aad86ce35561092dc0ee3af39765

Tx prefix hash: 35af50dd701c3278c1223e75152b2facd71a9cdc1b1f9b8a5371e5c9a88adf9f
Tx public key: 15f57f0c7b05a17ff2677e3dd634252da5bfb04af929b0de4f3d09edf7c681be
Timestamp: 1715479835 Timestamp [UCT]: 2024-05-12 02:10:35 Age [y:d:h:m:s]: 00:333:06:23:41
Block: 1020116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238183 RingCT/type: yes/0
Extra: 0115f57f0c7b05a17ff2677e3dd634252da5bfb04af929b0de4f3d09edf7c681be021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67764ebb4db41d68d428cb6a32fef00c85f62424fb664a8e1eb7157020dffd40 0.600000000000 1484175 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": 1020126, "vin": [ { "gen": { "height": 1020116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67764ebb4db41d68d428cb6a32fef00c85f62424fb664a8e1eb7157020dffd40" } } ], "extra": [ 1, 21, 245, 127, 12, 123, 5, 161, 127, 242, 103, 126, 61, 214, 52, 37, 45, 165, 191, 176, 74, 249, 41, 176, 222, 79, 61, 9, 237, 247, 198, 129, 190, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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