Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e738c48ca8df50d30f93ab7b883072239fa5aac2fe66b5fd7f46acb88bb40096

Tx prefix hash: 8975b15ec9fd5bee3714c258355e7c35331a1bda65701fc0e032ac79a043b9c9
Tx public key: ea9f2bc419cb51ec6419cf0fec53e87779fc7c65080c94601e47bd76d2a52d57
Timestamp: 1660962433 Timestamp [UCT]: 2022-08-20 02:27:13 Age [y:d:h:m:s]: 02:126:02:25:43
Block: 569651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611588 RingCT/type: yes/0
Extra: 01ea9f2bc419cb51ec6419cf0fec53e87779fc7c65080c94601e47bd76d2a52d57021100000007faf35c9c000000000000000000

1 output(s) for total of 7.952613335000 dcy

stealth address amount amount idx
00: 670f74352fa5ff4119ca323a4b9c14de5289d0ceed097491afa64fb2c6a06888 7.952613335000 1002808 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": 569661, "vin": [ { "gen": { "height": 569651 } } ], "vout": [ { "amount": 7952613335, "target": { "key": "670f74352fa5ff4119ca323a4b9c14de5289d0ceed097491afa64fb2c6a06888" } } ], "extra": [ 1, 234, 159, 43, 196, 25, 203, 81, 236, 100, 25, 207, 15, 236, 83, 232, 119, 121, 252, 124, 101, 8, 12, 148, 96, 30, 71, 189, 118, 210, 165, 45, 87, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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