Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382f6ec5b66c49aa29c6d25ddeb5c53036ca6472aa6d48e7ac49291322aebe6c

Tx prefix hash: 9411246b877e3853f5a76974ccdbeb5a966e2a4bf6efe45ce5d0ea210eb84d7f
Tx public key: 4c6f059d22af0aeca1cb7a3832f165aeb0f714a4d08f63e4ed6da324281e18d5
Timestamp: 1635381454 Timestamp [UCT]: 2021-10-28 00:37:34 Age [y:d:h:m:s]: 02:343:07:45:20
Block: 361878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 762964 RingCT/type: yes/0
Extra: 014c6f059d22af0aeca1cb7a3832f165aeb0f714a4d08f63e4ed6da324281e18d50211000000166e80e2c6000000000000000000

1 output(s) for total of 38.810422400000 dcy

stealth address amount amount idx
00: 121440343c79f001c9e22c1e12bc325434fe95bba31bab1bdd6f5a211e2cc857 38.810422400000 736050 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": 361888, "vin": [ { "gen": { "height": 361878 } } ], "vout": [ { "amount": 38810422400, "target": { "key": "121440343c79f001c9e22c1e12bc325434fe95bba31bab1bdd6f5a211e2cc857" } } ], "extra": [ 1, 76, 111, 5, 157, 34, 175, 10, 236, 161, 203, 122, 56, 50, 241, 101, 174, 176, 247, 20, 164, 208, 143, 99, 228, 237, 109, 163, 36, 40, 30, 24, 213, 2, 17, 0, 0, 0, 22, 110, 128, 226, 198, 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