Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e795efba0914b3822950f8cb88f1b3a2dfda405ef5fd3ef173cd74f9c9b0343

Tx prefix hash: a927adb6b3ff40e828758902b306c63114332ee459b5a764b7fe8932311bb621
Tx public key: 0ba9a56b2b5e46e50ca5df0a9b3a90d6b394fb840034f2d999542ad171ca5f06
Timestamp: 1617096051 Timestamp [UCT]: 2021-03-30 09:20:51 Age [y:d:h:m:s]: 04:216:00:33:27
Block: 229606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172249 RingCT/type: yes/0
Extra: 010ba9a56b2b5e46e50ca5df0a9b3a90d6b394fb840034f2d999542ad171ca5f060211000000b50dc70aa7000000000000000000

1 output(s) for total of 106.468366322000 dcy

stealth address amount amount idx
00: 71555bbf12d2c7d8073cffd31bb15aede7a0fd9fa077e50bd5675a68c3981a9b 106.468366322000 476466 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": 229616, "vin": [ { "gen": { "height": 229606 } } ], "vout": [ { "amount": 106468366322, "target": { "key": "71555bbf12d2c7d8073cffd31bb15aede7a0fd9fa077e50bd5675a68c3981a9b" } } ], "extra": [ 1, 11, 169, 165, 107, 43, 94, 70, 229, 12, 165, 223, 10, 155, 58, 144, 214, 179, 148, 251, 132, 0, 52, 242, 217, 153, 84, 42, 209, 113, 202, 95, 6, 2, 17, 0, 0, 0, 181, 13, 199, 10, 167, 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