Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6fbf0f6b9dcebc858f3fd291fd75810fd09e2a7b60351a9e00c12168c4d3d2b

Tx prefix hash: bdfba0e609678e04a67393e6e5d6124a7aeeb3da877edd2cc483e53ec662e64d
Tx public key: fa189c0e647ec9fcc566f952b2e6207e10c84cbff31163be2191b034721aff5e
Timestamp: 1765369507 Timestamp [UCT]: 2025-12-10 12:25:07 Age [y:d:h:m:s]: 00:019:01:56:10
Block: 1430555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13665 RingCT/type: yes/0
Extra: 01fa189c0e647ec9fcc566f952b2e6207e10c84cbff31163be2191b034721aff5e02110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dce362b085b86b93083a8ab8937c24c31fb18cd2120fb6b3ca8c6d4856bac2fd 0.600000000000 1919306 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": 1430565, "vin": [ { "gen": { "height": 1430555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dce362b085b86b93083a8ab8937c24c31fb18cd2120fb6b3ca8c6d4856bac2fd" } } ], "extra": [ 1, 250, 24, 156, 14, 100, 126, 201, 252, 197, 102, 249, 82, 178, 230, 32, 126, 16, 200, 76, 191, 243, 17, 99, 190, 33, 145, 176, 52, 114, 26, 255, 94, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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