Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fcf899d5862fce3dc7743b624c2cf693047a1384fe505571ae61d76e18e1940

Tx prefix hash: 6b574b011520c1f9f1d1cedd666c1367a0e96f04cd962261f89de4a52baeaaae
Tx public key: 0c40ef9aaf25a28a795b1ad2088032dbe3d9128a05195cc6f1411f1575c6a2e4
Timestamp: 1740688346 Timestamp [UCT]: 2025-02-27 20:32:26 Age [y:d:h:m:s]: 00:266:11:14:01
Block: 1228599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188201 RingCT/type: yes/0
Extra: 010c40ef9aaf25a28a795b1ad2088032dbe3d9128a05195cc6f1411f1575c6a2e40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63cf7fc6397e7ff72ddb292cd6079f6509873c415fcae8f9ad8f76f9a7611e3c 0.600000000000 1715480 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": 1228609, "vin": [ { "gen": { "height": 1228599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63cf7fc6397e7ff72ddb292cd6079f6509873c415fcae8f9ad8f76f9a7611e3c" } } ], "extra": [ 1, 12, 64, 239, 154, 175, 37, 162, 138, 121, 91, 26, 210, 8, 128, 50, 219, 227, 217, 18, 138, 5, 25, 92, 198, 241, 65, 31, 21, 117, 198, 162, 228, 2, 17, 0, 0, 0, 3, 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