Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909d173cc9c33c4e006a646d0a866fb20055dfeb51cd13d0d1dc5eb2b2d47192

Tx prefix hash: 90279c7daa7f731a8caed6befad14bea40a5569e38bc4b44f376e86ebf93a13b
Tx public key: 76d7f705e508f6aa0ba977e3ab67cb4ac9435d52b979a0187804bc9b5b569535
Timestamp: 1753214565 Timestamp [UCT]: 2025-07-22 20:02:45 Age [y:d:h:m:s]: 00:067:23:11:58
Block: 1331170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47313 RingCT/type: yes/0
Extra: 0176d7f705e508f6aa0ba977e3ab67cb4ac9435d52b979a0187804bc9b5b569535021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55792fcef9bb35e9ef7dafca22a05149beacc85d04f425c695da099e49919d57 0.600000000000 1818963 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": 1331180, "vin": [ { "gen": { "height": 1331170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55792fcef9bb35e9ef7dafca22a05149beacc85d04f425c695da099e49919d57" } } ], "extra": [ 1, 118, 215, 247, 5, 229, 8, 246, 170, 11, 169, 119, 227, 171, 103, 203, 74, 201, 67, 93, 82, 185, 121, 160, 24, 120, 4, 188, 155, 91, 86, 149, 53, 2, 17, 0, 0, 0, 4, 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