Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3679377d763dd5acbca5573e948f60297e4f90a50ab2bade6f63f536e723ec1

Tx prefix hash: 85fc9cf9884d78d9388139b338e46999a69b86b4f99dc2edd148ad29d1fb0c51
Tx public key: f04ac1a863303688a743efee932aa415d808b2055bc0cb5bb252e53fa426b64a
Timestamp: 1734203343 Timestamp [UCT]: 2024-12-14 19:09:03 Age [y:d:h:m:s]: 00:088:05:06:37
Block: 1175219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62817 RingCT/type: yes/0
Extra: 01f04ac1a863303688a743efee932aa415d808b2055bc0cb5bb252e53fa426b64a0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b6085051e0f7be9628fed4a7ede6f92335c4e8c2135d8f6417818e4ecaf5f5 0.600000000000 1661468 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": 1175229, "vin": [ { "gen": { "height": 1175219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b6085051e0f7be9628fed4a7ede6f92335c4e8c2135d8f6417818e4ecaf5f5" } } ], "extra": [ 1, 240, 74, 193, 168, 99, 48, 54, 136, 167, 67, 239, 238, 147, 42, 164, 21, 216, 8, 178, 5, 91, 192, 203, 91, 178, 82, 229, 63, 164, 38, 182, 74, 2, 17, 0, 0, 0, 8, 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