Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f181d963d331035ab28c32b54035acb0d0a5617d5955a75982e682046c473af4

Tx prefix hash: 6aaadba72066358aa8a48f918d947bee47baa3341add3db293784aac761ab262
Tx public key: 38853a7a711d5210efa1fc9f04a94818f933fe58d4c33eb29feaa89ce5f2d17f
Timestamp: 1688380108 Timestamp [UCT]: 2023-07-03 10:28:28 Age [y:d:h:m:s]: 01:145:05:30:22
Block: 795668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365128 RingCT/type: yes/0
Extra: 0138853a7a711d5210efa1fc9f04a94818f933fe58d4c33eb29feaa89ce5f2d17f02110000000133af99f4000000000000000000

1 output(s) for total of 1.417822143000 dcy

stealth address amount amount idx
00: ba3022ed3a26adf832eaeb62f82ae5a7a5288ee4706beded3540a74f2019b454 1.417822143000 1246491 of 0

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": 795678, "vin": [ { "gen": { "height": 795668 } } ], "vout": [ { "amount": 1417822143, "target": { "key": "ba3022ed3a26adf832eaeb62f82ae5a7a5288ee4706beded3540a74f2019b454" } } ], "extra": [ 1, 56, 133, 58, 122, 113, 29, 82, 16, 239, 161, 252, 159, 4, 169, 72, 24, 249, 51, 254, 88, 212, 195, 62, 178, 159, 234, 168, 156, 229, 242, 209, 127, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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