Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0719d27c1bc1f9de23cf447e525c7522d524ca13a8959aed987eeaff14d96ce3

Tx prefix hash: ec355a9195b14e2a5736e43da8f0a0a526f604009792e9e82e96bac735d4876e
Tx public key: dca23187cb5df50949e0aa3aba4b7c8aa3f924418736e565b8b9d833eeaab489
Timestamp: 1734947522 Timestamp [UCT]: 2024-12-23 09:52:02 Age [y:d:h:m:s]: 00:081:07:15:11
Block: 1181389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57872 RingCT/type: yes/0
Extra: 01dca23187cb5df50949e0aa3aba4b7c8aa3f924418736e565b8b9d833eeaab489021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da592d45ae14a97080438caa9aba2d7bfadb11b20912c57b7909e34fef7392b 0.600000000000 1667808 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": 1181399, "vin": [ { "gen": { "height": 1181389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da592d45ae14a97080438caa9aba2d7bfadb11b20912c57b7909e34fef7392b" } } ], "extra": [ 1, 220, 162, 49, 135, 203, 93, 245, 9, 73, 224, 170, 58, 186, 75, 124, 138, 163, 249, 36, 65, 135, 54, 229, 101, 184, 185, 216, 51, 238, 170, 180, 137, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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