Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a32247239ba228cec5eee6996849b97219b2170de8934c4e6483d2f7f811a5d9

Tx prefix hash: 9471e69a8fa06ff05c62e116ae038a4c91bee4757b7070087ca055746fbf7768
Tx public key: b2b2e588f2604acf0b3241df62d3ac38998879c2a63d9d9720cf28a340923456
Timestamp: 1577959592 Timestamp [UCT]: 2020-01-02 10:06:32 Age [y:d:h:m:s]: 04:262:06:40:49
Block: 37121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076514 RingCT/type: yes/0
Extra: 01b2b2e588f2604acf0b3241df62d3ac38998879c2a63d9d9720cf28a34092345602110000010531ef32d6000000000000000000

1 output(s) for total of 462.384821432000 dcy

stealth address amount amount idx
00: c5cd653b0f80c4f9dce9bbf179bcc602433f1890cf659c2b465dfb400118f906 462.384821432000 62943 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": 37131, "vin": [ { "gen": { "height": 37121 } } ], "vout": [ { "amount": 462384821432, "target": { "key": "c5cd653b0f80c4f9dce9bbf179bcc602433f1890cf659c2b465dfb400118f906" } } ], "extra": [ 1, 178, 178, 229, 136, 242, 96, 74, 207, 11, 50, 65, 223, 98, 211, 172, 56, 153, 136, 121, 194, 166, 61, 157, 151, 32, 207, 40, 163, 64, 146, 52, 86, 2, 17, 0, 0, 1, 5, 49, 239, 50, 214, 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