Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1147e654cf6760b7e7ccc309f0a442f1947fc9ab1f84ea00611b2f182b0748c4

Tx prefix hash: 08f0908219a0d978e618e59c081f7abd4c392c3ebef5807c641c7bec4a19e6e1
Tx public key: 43c9bd7eaea4e8bb8c594095f05da9f210591559e0361a77a12c971a9da69227
Timestamp: 1713331280 Timestamp [UCT]: 2024-04-17 05:21:20 Age [y:d:h:m:s]: 01:038:23:10:10
Block: 1002253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288835 RingCT/type: yes/0
Extra: 0143c9bd7eaea4e8bb8c594095f05da9f210591559e0361a77a12c971a9da692270211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b52f159cbec0264b594be65bfb3d9b6df0e1ef1fd184a3f2a0ea76826e9ba64 0.600000000000 1462769 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": 1002263, "vin": [ { "gen": { "height": 1002253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b52f159cbec0264b594be65bfb3d9b6df0e1ef1fd184a3f2a0ea76826e9ba64" } } ], "extra": [ 1, 67, 201, 189, 126, 174, 164, 232, 187, 140, 89, 64, 149, 240, 93, 169, 242, 16, 89, 21, 89, 224, 54, 26, 119, 161, 44, 151, 26, 157, 166, 146, 39, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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