Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3391874991d860c08e1c6881bb04628d055f2c0781acc5c935c936e5b5ab158f

Tx prefix hash: 79d6fff30d3b0f9c758da2b7a87fe1bc621c0e0191ea92cc4b01b1c6b9725c20
Tx public key: 0e0d583d5ddc27b0cc616d48e8a27b2d2987180fe0ca1c0c4708c1e3bcde26f2
Timestamp: 1725036009 Timestamp [UCT]: 2024-08-30 16:40:09 Age [y:d:h:m:s]: 00:245:08:13:57
Block: 1099294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175223 RingCT/type: yes/0
Extra: 010e0d583d5ddc27b0cc616d48e8a27b2d2987180fe0ca1c0c4708c1e3bcde26f202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70c6991c08c42c4f6fbf989a0600f3cdf64a7cdfbeb6a4f360106214364bec4d 0.600000000000 1575253 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": 1099304, "vin": [ { "gen": { "height": 1099294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70c6991c08c42c4f6fbf989a0600f3cdf64a7cdfbeb6a4f360106214364bec4d" } } ], "extra": [ 1, 14, 13, 88, 61, 93, 220, 39, 176, 204, 97, 109, 72, 232, 162, 123, 45, 41, 135, 24, 15, 224, 202, 28, 12, 71, 8, 193, 227, 188, 222, 38, 242, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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