Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3339a078e38181eb989a3e389111f09ebdb22d7a68a77a56610c47d5ce2bca3b

Tx prefix hash: 60dd7379e54e253ed220d5c0cc9879e2e9627b80a33ec63540b8ab386bfe35cc
Tx public key: a05233fe89a278b6939efbd8e9d24c8b9590f9a3c1f6ab54461eecb417ac4638
Timestamp: 1720490912 Timestamp [UCT]: 2024-07-09 02:08:32 Age [y:d:h:m:s]: 00:277:05:52:24
Block: 1061637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198078 RingCT/type: yes/0
Extra: 01a05233fe89a278b6939efbd8e9d24c8b9590f9a3c1f6ab54461eecb417ac4638021100000003c26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41bc54d32298756e5349c3f3a3bf4abfdbfb8fb3caf3a16663fb04632fd7e40b 0.600000000000 1532130 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": 1061647, "vin": [ { "gen": { "height": 1061637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41bc54d32298756e5349c3f3a3bf4abfdbfb8fb3caf3a16663fb04632fd7e40b" } } ], "extra": [ 1, 160, 82, 51, 254, 137, 162, 120, 182, 147, 158, 251, 216, 233, 210, 76, 139, 149, 144, 249, 163, 193, 246, 171, 84, 70, 30, 236, 180, 23, 172, 70, 56, 2, 17, 0, 0, 0, 3, 194, 109, 58, 153, 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