Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25cda2210c4656ff502ae8dc22c20307a750e2c19d72b60a5f56bbe38f06860b

Tx prefix hash: 64b270fff91176ab2e9ee0e93d04d6d83d013a0999c00e2d1caab9c700f29a14
Tx public key: 54304253d27f4e38a087a050b5ed8c62a95b2e4034776ee01a89daffae4315ee
Timestamp: 1726488525 Timestamp [UCT]: 2024-09-16 12:08:45 Age [y:d:h:m:s]: 00:207:07:40:17
Block: 1111346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148009 RingCT/type: yes/0
Extra: 0154304253d27f4e38a087a050b5ed8c62a95b2e4034776ee01a89daffae4315ee021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b020022b29eeff6c3dd98fc710f40263a6ea8093ff27b2a85a78dc2d0aef4b 0.600000000000 1590273 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": 1111356, "vin": [ { "gen": { "height": 1111346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b020022b29eeff6c3dd98fc710f40263a6ea8093ff27b2a85a78dc2d0aef4b" } } ], "extra": [ 1, 84, 48, 66, 83, 210, 127, 78, 56, 160, 135, 160, 80, 181, 237, 140, 98, 169, 91, 46, 64, 52, 119, 110, 224, 26, 137, 218, 255, 174, 67, 21, 238, 2, 17, 0, 0, 0, 3, 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