Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551c827a71739ca8c77d9935e84526e490e608db966dcfc85865b0e75d3aba1d

Tx prefix hash: 25e645700884a5e68b5fb9f07163dc60c64fde4b95cdafb3f4ef8f2f758cfb21
Tx public key: f1b1b26f88a150c638c54d1f6ba96a49af139a4a69f5fdc89b2f7e021d603dff
Timestamp: 1623775767 Timestamp [UCT]: 2021-06-15 16:49:27 Age [y:d:h:m:s]: 03:332:01:00:30
Block: 278377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1003085 RingCT/type: yes/0
Extra: 01f1b1b26f88a150c638c54d1f6ba96a49af139a4a69f5fdc89b2f7e021d603dff021100000005ece3035d000000000000000000

1 output(s) for total of 73.387477624000 dcy

stealth address amount amount idx
00: 272f5386e8c74acff852f4d877ef4cf31312fce7fd04660badc2ad1d07351e71 73.387477624000 583337 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": 278387, "vin": [ { "gen": { "height": 278377 } } ], "vout": [ { "amount": 73387477624, "target": { "key": "272f5386e8c74acff852f4d877ef4cf31312fce7fd04660badc2ad1d07351e71" } } ], "extra": [ 1, 241, 177, 178, 111, 136, 161, 80, 198, 56, 197, 77, 31, 107, 169, 106, 73, 175, 19, 154, 74, 105, 245, 253, 200, 155, 47, 126, 2, 29, 96, 61, 255, 2, 17, 0, 0, 0, 5, 236, 227, 3, 93, 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