Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57bc28a68301c1f2fd47049d5e3877f807a2fcac50a50aca56aec6a5c529f0e0

Tx prefix hash: 24335d76f20136ac6216716ca5c5873459a8574bb76fd64aa646d8c2acd327c3
Tx public key: 838ab5fcda4fb29a7cdbadae98fc3a605d8d31f1b475284e631e3c266d0a84ef
Timestamp: 1725020792 Timestamp [UCT]: 2024-08-30 12:26:32 Age [y:d:h:m:s]: 00:292:06:17:18
Block: 1099176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208651 RingCT/type: yes/0
Extra: 01838ab5fcda4fb29a7cdbadae98fc3a605d8d31f1b475284e631e3c266d0a84ef021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86a5a09077ab4dca27d391270cacc54565d117b295a9fbfb411ff1f15bc6f060 0.600000000000 1575105 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": 1099186, "vin": [ { "gen": { "height": 1099176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86a5a09077ab4dca27d391270cacc54565d117b295a9fbfb411ff1f15bc6f060" } } ], "extra": [ 1, 131, 138, 181, 252, 218, 79, 178, 154, 124, 219, 173, 174, 152, 252, 58, 96, 93, 141, 49, 241, 180, 117, 40, 78, 99, 30, 60, 38, 109, 10, 132, 239, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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