Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1b155800b2a689e1aef3e49694d1a0c6d9fa1f3a439a1c4c9ba1ca06ecfc06

Tx prefix hash: aeaed9eb1ff147bf2c4d245177cbbacaf16af45b0339b19f6662833df316b863
Tx public key: 1fe37513acc7e0067e7df2a1cd4327c03aefcad5ad3c5e4749d41620da10630a
Timestamp: 1737344995 Timestamp [UCT]: 2025-01-20 03:49:55 Age [y:d:h:m:s]: 00:331:01:39:12
Block: 1201161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234195 RingCT/type: yes/0
Extra: 011fe37513acc7e0067e7df2a1cd4327c03aefcad5ad3c5e4749d41620da10630a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 874c712c1bc9b8b6c8d03068f501b634e8e4e66fc0d40909975bcac9dca7de59 0.600000000000 1687810 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": 1201171, "vin": [ { "gen": { "height": 1201161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "874c712c1bc9b8b6c8d03068f501b634e8e4e66fc0d40909975bcac9dca7de59" } } ], "extra": [ 1, 31, 227, 117, 19, 172, 199, 224, 6, 126, 125, 242, 161, 205, 67, 39, 192, 58, 239, 202, 213, 173, 60, 94, 71, 73, 212, 22, 32, 218, 16, 99, 10, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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