Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a31039a304867f246c4d60fc66182932bb277328062f02421b7bcce6206f99d

Tx prefix hash: e27a0a169e8ddd333b004bb885cbf5e1122b60a745a1e24623f537815a3f9977
Tx public key: b96a7471c70dc9fbbd927cfe0ce616c78d30223b2d2815ad02aacb8faf576f3e
Timestamp: 1732085060 Timestamp [UCT]: 2024-11-20 06:44:20 Age [y:d:h:m:s]: 00:003:23:36:39
Block: 1157639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2856 RingCT/type: yes/0
Extra: 01b96a7471c70dc9fbbd927cfe0ce616c78d30223b2d2815ad02aacb8faf576f3e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa42739beb704e3207cb3f1049dac503828181d897fdd1feee819f14cf73655 0.600000000000 1643262 of 15

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": 1157649, "vin": [ { "gen": { "height": 1157639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa42739beb704e3207cb3f1049dac503828181d897fdd1feee819f14cf73655" } } ], "extra": [ 1, 185, 106, 116, 113, 199, 13, 201, 251, 189, 146, 124, 254, 12, 230, 22, 199, 141, 48, 34, 59, 45, 40, 21, 173, 2, 170, 203, 143, 175, 87, 111, 62, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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