Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8aaabeabc49346a4401beea79d37a2c1db50d3dfe91f388574294daa5828a07

Tx prefix hash: 4a5cc896fc4c6b1100844c45cbf84e6a987e34d67caa5f0012a77badf2b53435
Tx public key: d14d71a2a86be2d70ba15e99272fc366408f439e3f34b5ed6b6b855d90b66702
Timestamp: 1702639924 Timestamp [UCT]: 2023-12-15 11:32:04 Age [y:d:h:m:s]: 01:158:12:45:05
Block: 913628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374480 RingCT/type: yes/0
Extra: 01d14d71a2a86be2d70ba15e99272fc366408f439e3f34b5ed6b6b855d90b66702021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e31991935cd6f3a91551dbbfca9d1f9640fecf11e2bc3f902a51c3608c1275 0.600000000000 1370904 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": 913638, "vin": [ { "gen": { "height": 913628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e31991935cd6f3a91551dbbfca9d1f9640fecf11e2bc3f902a51c3608c1275" } } ], "extra": [ 1, 209, 77, 113, 162, 168, 107, 226, 215, 11, 161, 94, 153, 39, 47, 195, 102, 64, 143, 67, 158, 63, 52, 181, 237, 107, 107, 133, 93, 144, 182, 103, 2, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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