Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2fdf228ce23bf5e776a452e89258623cb717038d9aa43b83e1f7c893e3a6091

Tx prefix hash: 729810c76c040640f0f197e1e1d8ce1d60d88dc777a6900fa2e6a91ff4340b7a
Tx public key: 7af97355919a3d9283bdd9956178327fe85b065428e8b3fe00b53162cc9bd379
Timestamp: 1752106232 Timestamp [UCT]: 2025-07-10 00:10:32 Age [y:d:h:m:s]: 00:183:06:34:20
Block: 1322243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129628 RingCT/type: yes/0
Extra: 017af97355919a3d9283bdd9956178327fe85b065428e8b3fe00b53162cc9bd379021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca3e2d4e4a86fff2f8d9b94e50bb221777c71432083012d8fbdb9feafb7e75ed 0.600000000000 1809970 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": 1322253, "vin": [ { "gen": { "height": 1322243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca3e2d4e4a86fff2f8d9b94e50bb221777c71432083012d8fbdb9feafb7e75ed" } } ], "extra": [ 1, 122, 249, 115, 85, 145, 154, 61, 146, 131, 189, 217, 149, 97, 120, 50, 127, 232, 91, 6, 84, 40, 232, 179, 254, 0, 181, 49, 98, 204, 155, 211, 121, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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