Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092026f0ea6929df104d6b2a705627b329880da957b1a370222d088136ab6865

Tx prefix hash: f068e66c037ce198d57f1f9d1f2f6a7d4112d94476c9f669b3aa5d9a0c48face
Tx public key: f3153586a23453e120bb6de945bdc3bb0373d404ff16a367a1d0566e70d40965
Timestamp: 1723433535 Timestamp [UCT]: 2024-08-12 03:32:15 Age [y:d:h:m:s]: 00:217:08:50:28
Block: 1086018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155248 RingCT/type: yes/0
Extra: 01f3153586a23453e120bb6de945bdc3bb0373d404ff16a367a1d0566e70d4096502110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aba2f1a5aae23418737a17cc84b5569180455e7128028b8676c7d8b2a5c8fb4 0.600000000000 1560611 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": 1086028, "vin": [ { "gen": { "height": 1086018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aba2f1a5aae23418737a17cc84b5569180455e7128028b8676c7d8b2a5c8fb4" } } ], "extra": [ 1, 243, 21, 53, 134, 162, 52, 83, 225, 32, 187, 109, 233, 69, 189, 195, 187, 3, 115, 212, 4, 255, 22, 163, 103, 161, 208, 86, 110, 112, 212, 9, 101, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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