Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b3f20e22ace09ab97ed91068473e69c68d5cae76091c3326545dba0114d366

Tx prefix hash: e8e92a787154813d45b8a0416e6d367e364c0bfea9b95668b900031fffc8c759
Tx public key: 0cab4b72c36860d37100e5766f352c4b6b9103cd2fbde77084eecda7db609eab
Timestamp: 1706545261 Timestamp [UCT]: 2024-01-29 16:21:01 Age [y:d:h:m:s]: 01:087:22:06:13
Block: 945988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323938 RingCT/type: yes/0
Extra: 010cab4b72c36860d37100e5766f352c4b6b9103cd2fbde77084eecda7db609eab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cebbd41a9ec517f8b3ee267c7daa88903cdfdcb5e2a5c1ae0a035241c44c3789 0.600000000000 1404318 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": 945998, "vin": [ { "gen": { "height": 945988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cebbd41a9ec517f8b3ee267c7daa88903cdfdcb5e2a5c1ae0a035241c44c3789" } } ], "extra": [ 1, 12, 171, 75, 114, 195, 104, 96, 211, 113, 0, 229, 118, 111, 53, 44, 75, 107, 145, 3, 205, 47, 189, 231, 112, 132, 238, 205, 167, 219, 96, 158, 171, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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