Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 897dfea8fa475be6827e84e1b80a41bf6daadb75c105815ca1b4837c565a576d

Tx prefix hash: b8f3036885e921323c9f63f7b5c8ee55f0e484fef1b6d26487436b011260ecad
Tx public key: 45cc65e54d64fbe3d271e556b26171338bb4e4c519e73a80d3c6a338b0169a17
Timestamp: 1748910998 Timestamp [UCT]: 2025-06-03 00:36:38 Age [y:d:h:m:s]: 00:171:22:35:37
Block: 1296696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120571 RingCT/type: yes/0
Extra: 0145cc65e54d64fbe3d271e556b26171338bb4e4c519e73a80d3c6a338b0169a1702110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a41f72a742b5ef1fba7d08a28b40ee21a6f74404b03b0f50593f6ebf6bcc971 0.600000000000 1784209 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": 1296706, "vin": [ { "gen": { "height": 1296696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a41f72a742b5ef1fba7d08a28b40ee21a6f74404b03b0f50593f6ebf6bcc971" } } ], "extra": [ 1, 69, 204, 101, 229, 77, 100, 251, 227, 210, 113, 229, 86, 178, 97, 113, 51, 139, 180, 228, 197, 25, 231, 58, 128, 211, 198, 163, 56, 176, 22, 154, 23, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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