Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 628c5f3c714c71eaf1b02f5792e931a3230dd92877fa9eac4f58b041524df05c

Tx prefix hash: 99f6ff3bd79884815e8f5ceee0f5a9752e8a1f4315faae653c8c38ab6415bebc
Tx public key: e9d2d6a6b0979b9ba01524ff7ee58d20f38160002bb70008420fce0f51b2e450
Timestamp: 1622221038 Timestamp [UCT]: 2021-05-28 16:57:18 Age [y:d:h:m:s]: 03:211:23:45:50
Block: 268356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914644 RingCT/type: yes/0
Extra: 01e9d2d6a6b0979b9ba01524ff7ee58d20f38160002bb70008420fce0f51b2e4500211000000036e2c823c000000000000000000

1 output(s) for total of 79.218334646000 dcy

stealth address amount amount idx
00: d47399cb43688fbadd95d8d74c6ee58b5c0b9a0e9daa8d294ecb89b5f8f82f5c 79.218334646000 563608 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": 268366, "vin": [ { "gen": { "height": 268356 } } ], "vout": [ { "amount": 79218334646, "target": { "key": "d47399cb43688fbadd95d8d74c6ee58b5c0b9a0e9daa8d294ecb89b5f8f82f5c" } } ], "extra": [ 1, 233, 210, 214, 166, 176, 151, 155, 155, 160, 21, 36, 255, 126, 229, 141, 32, 243, 129, 96, 0, 43, 183, 0, 8, 66, 15, 206, 15, 81, 178, 228, 80, 2, 17, 0, 0, 0, 3, 110, 44, 130, 60, 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