Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed9efed27c81c4d3f2d4b3a72cb989519bddd54dc635f41697028d2b9e798338

Tx prefix hash: 0328ce1e8baf7d81f2a92410351d82a7632757e6378796ea888c436fa9491685
Tx public key: 61945ef1bcbe6e3e5ac3f36c35ae2e625e8c4ba5d68e631dc87f87a3b74105bb
Timestamp: 1583538008 Timestamp [UCT]: 2020-03-06 23:40:08 Age [y:d:h:m:s]: 04:268:12:53:32
Block: 77860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086415 RingCT/type: yes/0
Extra: 0161945ef1bcbe6e3e5ac3f36c35ae2e625e8c4ba5d68e631dc87f87a3b74105bb02110000001ad76d46ee000000000000000000

1 output(s) for total of 338.858428068000 dcy

stealth address amount amount idx
00: 8f2cc37c78c184f4edf201a538d3e9be17dc39af9106ef1cf11fb6846a752398 338.858428068000 143087 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": 77870, "vin": [ { "gen": { "height": 77860 } } ], "vout": [ { "amount": 338858428068, "target": { "key": "8f2cc37c78c184f4edf201a538d3e9be17dc39af9106ef1cf11fb6846a752398" } } ], "extra": [ 1, 97, 148, 94, 241, 188, 190, 110, 62, 90, 195, 243, 108, 53, 174, 46, 98, 94, 140, 75, 165, 214, 142, 99, 29, 200, 127, 135, 163, 183, 65, 5, 187, 2, 17, 0, 0, 0, 26, 215, 109, 70, 238, 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