Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8b5bfaa07baf22e445509941ed4fdd68686e74a98d70dfb3fd8f4f66af02f1

Tx prefix hash: 3e86dda67407ae140a6a6abd8710004d80471c033be21a9aabd28a42e03d356f
Tx public key: b1db76008b6ab219fe9f1dd90d02b9b846dc57418fd978c6a8ca4f67542ce087
Timestamp: 1636958320 Timestamp [UCT]: 2021-11-15 06:38:40 Age [y:d:h:m:s]: 03:164:15:56:25
Block: 374651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896230 RingCT/type: yes/0
Extra: 01b1db76008b6ab219fe9f1dd90d02b9b846dc57418fd978c6a8ca4f67542ce087021100000031e9564d6f000000000000000000

1 output(s) for total of 35.206763218000 dcy

stealth address amount amount idx
00: 17eec4e8946ce539302c1fd51fd402d9cf12ba01df4162e63a3b314e5be7780c 35.206763218000 758273 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": 374661, "vin": [ { "gen": { "height": 374651 } } ], "vout": [ { "amount": 35206763218, "target": { "key": "17eec4e8946ce539302c1fd51fd402d9cf12ba01df4162e63a3b314e5be7780c" } } ], "extra": [ 1, 177, 219, 118, 0, 139, 106, 178, 25, 254, 159, 29, 217, 13, 2, 185, 184, 70, 220, 87, 65, 143, 217, 120, 198, 168, 202, 79, 103, 84, 44, 224, 135, 2, 17, 0, 0, 0, 49, 233, 86, 77, 111, 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