Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce8fcca67b24ac87f14624fde55edf70cf5f439b9cd76b557b671d79817e723

Tx prefix hash: f1d8a87a108a10b4bd1c5600a8f82f1f2561c4ae71325020b45a5c51e4de777e
Tx public key: bd271f5b79c63d87a4d0cefe3d13357f5063e62dfe8969398ca331a8b82c375c
Timestamp: 1708952314 Timestamp [UCT]: 2024-02-26 12:58:34 Age [y:d:h:m:s]: 01:025:01:50:55
Block: 965972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278929 RingCT/type: yes/0
Extra: 01bd271f5b79c63d87a4d0cefe3d13357f5063e62dfe8969398ca331a8b82c375c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4770ce93c1eb6dafe1fb1b009258eaf3171ddf2e8adde6bc74668273079f250 0.600000000000 1425727 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": 965982, "vin": [ { "gen": { "height": 965972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4770ce93c1eb6dafe1fb1b009258eaf3171ddf2e8adde6bc74668273079f250" } } ], "extra": [ 1, 189, 39, 31, 91, 121, 198, 61, 135, 164, 208, 206, 254, 61, 19, 53, 127, 80, 99, 230, 45, 254, 137, 105, 57, 140, 163, 49, 168, 184, 44, 55, 92, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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