Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f219a75bda1279b68c0630f60e3aed28808f1198425716e94fd14d3ee212c51d

Tx prefix hash: 3cdb5d959eee7a5cb267d67ffa616ed9fc9029c4a5e04b85cd5e7e2a3b88cf86
Tx public key: b42c8edc0ff403e41aaccd6dd911d0773310a6ca62dd51db72aea005281f5b93
Timestamp: 1694285613 Timestamp [UCT]: 2023-09-09 18:53:33 Age [y:d:h:m:s]: 01:168:01:59:23
Block: 844553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381197 RingCT/type: yes/0
Extra: 01b42c8edc0ff403e41aaccd6dd911d0773310a6ca62dd51db72aea005281f5b9302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.976439602000 dcy

stealth address amount amount idx
00: 68908ad68df764ce8d7d0d99e9a3479784d867dd6ed66f06cead1b4c5d938765 0.976439602000 1297871 of 0

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": 844563, "vin": [ { "gen": { "height": 844553 } } ], "vout": [ { "amount": 976439602, "target": { "key": "68908ad68df764ce8d7d0d99e9a3479784d867dd6ed66f06cead1b4c5d938765" } } ], "extra": [ 1, 180, 44, 142, 220, 15, 244, 3, 228, 26, 172, 205, 109, 217, 17, 208, 119, 51, 16, 166, 202, 98, 221, 81, 219, 114, 174, 160, 5, 40, 31, 91, 147, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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