Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345b09dc83a1d9c98eca9f31446e4604a3879f086c3434d413c8eb48eab75298

Tx prefix hash: bdaa61bbd7969ddf2a689aa0080b6e27ce87c97920efc1c7f3d567faf3c685e5
Tx public key: b24cd15a5cd78c1c36c9bedfef561ac0e4c06427a087db25505848c20e1a83e6
Timestamp: 1736175806 Timestamp [UCT]: 2025-01-06 15:03:26 Age [y:d:h:m:s]: 00:156:23:43:00
Block: 1191541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111970 RingCT/type: yes/0
Extra: 01b24cd15a5cd78c1c36c9bedfef561ac0e4c06427a087db25505848c20e1a83e602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f554929a9e1d8469ea8cc806a3551c4780f636eda274021a7ea3273bb020c9 0.600000000000 1678080 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": 1191551, "vin": [ { "gen": { "height": 1191541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f554929a9e1d8469ea8cc806a3551c4780f636eda274021a7ea3273bb020c9" } } ], "extra": [ 1, 178, 76, 209, 90, 92, 215, 140, 28, 54, 201, 190, 223, 239, 86, 26, 192, 228, 192, 100, 39, 160, 135, 219, 37, 80, 88, 72, 194, 14, 26, 131, 230, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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