Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933e9dc466f30221dbe834606380b4f6b33375a66dfc3b5d7320dc86a7039dd0

Tx prefix hash: 073d2ca2adc2a7577956dc9f1b2311991fe310379ac407cd09c40c5c575ad540
Tx public key: 9ec8ebc9203bb63a4d09069fec37a47e2d69303f7e5cf8d1e41a0ca3730f9ce4
Timestamp: 1728704328 Timestamp [UCT]: 2024-10-12 03:38:48 Age [y:d:h:m:s]: 00:004:17:23:29
Block: 1129734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3371 RingCT/type: yes/0
Extra: 019ec8ebc9203bb63a4d09069fec37a47e2d69303f7e5cf8d1e41a0ca3730f9ce4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ccff7aa6b6e1e4e14355b7829825ba683507c8472c74ee7a86affa9d4499132 0.600000000000 1612583 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": 1129744, "vin": [ { "gen": { "height": 1129734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ccff7aa6b6e1e4e14355b7829825ba683507c8472c74ee7a86affa9d4499132" } } ], "extra": [ 1, 158, 200, 235, 201, 32, 59, 182, 58, 77, 9, 6, 159, 236, 55, 164, 126, 45, 105, 48, 63, 126, 92, 248, 209, 228, 26, 12, 163, 115, 15, 156, 228, 2, 17, 0, 0, 0, 1, 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