Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9f5c172e67ca26d570c0f24832151801fb47df39e10a342f9c017456f5b969

Tx prefix hash: aa021aa60e68817f3eb06df7c91d18cd77400b7f4386ba71cd85e9da3ba71918
Tx public key: f8f90c1cf295abfc22cfbee7ec03f3eb32ff162f021ed65f8f2da4690682e5fc
Timestamp: 1748759725 Timestamp [UCT]: 2025-06-01 06:35:25 Age [y:d:h:m:s]: 00:162:18:39:28
Block: 1295448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114007 RingCT/type: yes/0
Extra: 01f8f90c1cf295abfc22cfbee7ec03f3eb32ff162f021ed65f8f2da4690682e5fc021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01384d8efd3d647d200500b84806af0d2f721596ef9f4eb4bb5eb9063ed3f52d 0.600000000000 1782951 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": 1295458, "vin": [ { "gen": { "height": 1295448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01384d8efd3d647d200500b84806af0d2f721596ef9f4eb4bb5eb9063ed3f52d" } } ], "extra": [ 1, 248, 249, 12, 28, 242, 149, 171, 252, 34, 207, 190, 231, 236, 3, 243, 235, 50, 255, 22, 47, 2, 30, 214, 95, 143, 45, 164, 105, 6, 130, 229, 252, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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