Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f357a5fe4f04be269bee91b700ab82b43b0f7d0d58221c1356770a3b27dc32

Tx prefix hash: 7a18846c71543c643bfaa71f2c922dda743e22254ad25094eaf32fe4a34af004
Tx public key: e9eca8067ec8570ddc8300f9443469e60d9b9eff2667908b42fb317a8fa5cb00
Timestamp: 1701063395 Timestamp [UCT]: 2023-11-27 05:36:35 Age [y:d:h:m:s]: 01:155:08:33:44
Block: 900557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372214 RingCT/type: yes/0
Extra: 01e9eca8067ec8570ddc8300f9443469e60d9b9eff2667908b42fb317a8fa5cb00021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.636914011000 dcy

stealth address amount amount idx
00: 27da06b0bcc06b4b445baf4fc32d92d6dd875eade91fd1ad8ab013f7c5a81763 0.636914011000 1357064 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": 900567, "vin": [ { "gen": { "height": 900557 } } ], "vout": [ { "amount": 636914011, "target": { "key": "27da06b0bcc06b4b445baf4fc32d92d6dd875eade91fd1ad8ab013f7c5a81763" } } ], "extra": [ 1, 233, 236, 168, 6, 126, 200, 87, 13, 220, 131, 0, 249, 68, 52, 105, 230, 13, 155, 158, 255, 38, 103, 144, 139, 66, 251, 49, 122, 143, 165, 203, 0, 2, 17, 0, 0, 0, 7, 230, 210, 127, 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