Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e971bf10100201577388e94fba4f92e40a425377345b6daa7e725b17d54a230a

Tx prefix hash: bf68c79acdc6fc9c7f13f5d9a67310ae9fab3ebc9561d0ed85c848335c6205bf
Tx public key: b07e7b3cedfbaef1d1e1d6ac1f72923cdd0aa33adbda79bac6bc00a6d978e702
Timestamp: 1634502035 Timestamp [UCT]: 2021-10-17 20:20:35 Age [y:d:h:m:s]: 03:043:22:27:50
Block: 355134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 809328 RingCT/type: yes/0
Extra: 01b07e7b3cedfbaef1d1e1d6ac1f72923cdd0aa33adbda79bac6bc00a6d978e702021100000001f29d7abf000000000000000000

1 output(s) for total of 40.860304373000 dcy

stealth address amount amount idx
00: 9f2c9f5dc5dc1af3b2ab304183d3a8c3600a4e47c5663ce4eed24a2f712b9ada 40.860304373000 725166 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": 355144, "vin": [ { "gen": { "height": 355134 } } ], "vout": [ { "amount": 40860304373, "target": { "key": "9f2c9f5dc5dc1af3b2ab304183d3a8c3600a4e47c5663ce4eed24a2f712b9ada" } } ], "extra": [ 1, 176, 126, 123, 60, 237, 251, 174, 241, 209, 225, 214, 172, 31, 114, 146, 60, 221, 10, 163, 58, 219, 218, 121, 186, 198, 188, 0, 166, 217, 120, 231, 2, 2, 17, 0, 0, 0, 1, 242, 157, 122, 191, 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