Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734a723917a66ac8a595c4a4c70bc292d0e69e84b9d508dce4a78d2f37062c4f

Tx prefix hash: c9f1bfb6d9080532e205f7c23d0046a896121ee747d34b27834e148335e1fc4f
Tx public key: b6bf5b06d9b2e5ea2121d67146e2b913638925b181eb473b112dabcb3da4d8f9
Timestamp: 1639282813 Timestamp [UCT]: 2021-12-12 04:20:13 Age [y:d:h:m:s]: 03:092:20:45:19
Block: 393660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 845122 RingCT/type: yes/0
Extra: 01b6bf5b06d9b2e5ea2121d67146e2b913638925b181eb473b112dabcb3da4d8f9021100000002117daff0000000000000000000

1 output(s) for total of 30.453791124000 dcy

stealth address amount amount idx
00: b90cc2108c33cf8e083a677fc6899341a75b8fdf6c13ccaf317fc31136fc33a9 30.453791124000 790967 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": 393670, "vin": [ { "gen": { "height": 393660 } } ], "vout": [ { "amount": 30453791124, "target": { "key": "b90cc2108c33cf8e083a677fc6899341a75b8fdf6c13ccaf317fc31136fc33a9" } } ], "extra": [ 1, 182, 191, 91, 6, 217, 178, 229, 234, 33, 33, 214, 113, 70, 226, 185, 19, 99, 137, 37, 177, 129, 235, 71, 59, 17, 45, 171, 203, 61, 164, 216, 249, 2, 17, 0, 0, 0, 2, 17, 125, 175, 240, 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