Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3d6e985e8415f2f573ccb8d9191275abf14ed97f46c1ba7bbf79db3db72791f

Tx prefix hash: 669ddf342eb9bfe2a3c743e6d03b8881e39905822f8bc774a5b262948e7f1162
Tx public key: 2a732f8ad149fa50c92e5348dbdf7bb30ab0708c60c9393a374f2bfdfedd9eb1
Timestamp: 1679819839 Timestamp [UCT]: 2023-03-26 08:37:19 Age [y:d:h:m:s]: 02:033:18:29:57
Block: 725345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545673 RingCT/type: yes/0
Extra: 012a732f8ad149fa50c92e5348dbdf7bb30ab0708c60c9393a374f2bfdfedd9eb102110000000152542ceb000000000000000000

1 output(s) for total of 2.424547998000 dcy

stealth address amount amount idx
00: 1d165dc532f2c20b31137a6e74bde7b6c9406b906ec60242a1d42a461234c605 2.424547998000 1170448 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": 725355, "vin": [ { "gen": { "height": 725345 } } ], "vout": [ { "amount": 2424547998, "target": { "key": "1d165dc532f2c20b31137a6e74bde7b6c9406b906ec60242a1d42a461234c605" } } ], "extra": [ 1, 42, 115, 47, 138, 209, 73, 250, 80, 201, 46, 83, 72, 219, 223, 123, 179, 10, 176, 112, 140, 96, 201, 57, 58, 55, 79, 43, 253, 254, 221, 158, 177, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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