Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07d4532af3a731fcc8be4875643380a4b34576c1ebe9cdf7a1977b1123cdb438

Tx prefix hash: 0f4b9213e9f07cde47553e3c66c13ea901067ef17739e12fc937c3d09cf8c7e4
Tx public key: 8a9958e5e21cee52ef45668813e46a0fdb954860fa68005d1a3db0aef7e53eca
Timestamp: 1638323912 Timestamp [UCT]: 2021-12-01 01:58:32 Age [y:d:h:m:s]: 03:339:00:56:48
Block: 385776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1018722 RingCT/type: yes/0
Extra: 018a9958e5e21cee52ef45668813e46a0fdb954860fa68005d1a3db0aef7e53eca02110000001ad6e4826b000000000000000000

1 output(s) for total of 32.342901461000 dcy

stealth address amount amount idx
00: fdc351a5f0afe0eda79b253b5901cf1a0e63399dc2b57929a33fbf75d3c74cea 32.342901461000 778443 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": 385786, "vin": [ { "gen": { "height": 385776 } } ], "vout": [ { "amount": 32342901461, "target": { "key": "fdc351a5f0afe0eda79b253b5901cf1a0e63399dc2b57929a33fbf75d3c74cea" } } ], "extra": [ 1, 138, 153, 88, 229, 226, 28, 238, 82, 239, 69, 102, 136, 19, 228, 106, 15, 219, 149, 72, 96, 250, 104, 0, 93, 26, 61, 176, 174, 247, 229, 62, 202, 2, 17, 0, 0, 0, 26, 214, 228, 130, 107, 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