Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03b7e8968b434145cccd1fc58fb7aa8049fea6343c561feb9154f11ef28b58fa

Tx prefix hash: 3ee7956e83b327265818e78d070eef7aa8b3355269f443dc580ba1f107cbf89b
Tx public key: ce339855bb0e87cc307b12bb1b5e418a568d97d5e3277b9210f1e4d308ea01db
Timestamp: 1744844683 Timestamp [UCT]: 2025-04-16 23:04:43 Age [y:d:h:m:s]: 00:216:16:28:43
Block: 1263017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152592 RingCT/type: yes/0
Extra: 01ce339855bb0e87cc307b12bb1b5e418a568d97d5e3277b9210f1e4d308ea01db0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44199a036b3315aee13f7978fd703ffc7da86b3ec545dc0a946e2a1e02a5068 0.600000000000 1750200 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": 1263027, "vin": [ { "gen": { "height": 1263017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44199a036b3315aee13f7978fd703ffc7da86b3ec545dc0a946e2a1e02a5068" } } ], "extra": [ 1, 206, 51, 152, 85, 187, 14, 135, 204, 48, 123, 18, 187, 27, 94, 65, 138, 86, 141, 151, 213, 227, 39, 123, 146, 16, 241, 228, 211, 8, 234, 1, 219, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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