Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc134c1a98245a85f97beb2df5e008f6f1946845b524c9f6df50fc4ba80bd4fd

Tx prefix hash: d54441f08df9a8a805f3ab6b7c956ad046b2dee11b50a42260b0ffe9327e3814
Tx public key: 49c409ae4bb91c1f22224254dd799b003b4ee296a4fd7296a859560c79f11f8d
Timestamp: 1749750193 Timestamp [UCT]: 2025-06-12 17:43:13 Age [y:d:h:m:s]: 00:230:13:01:49
Block: 1303601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162404 RingCT/type: yes/0
Extra: 0149c409ae4bb91c1f22224254dd799b003b4ee296a4fd7296a859560c79f11f8d02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 903e1477ae7d986056181d97639890c9b85898c946697e7872489b2a5c225603 0.600000000000 1791184 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": 1303611, "vin": [ { "gen": { "height": 1303601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "903e1477ae7d986056181d97639890c9b85898c946697e7872489b2a5c225603" } } ], "extra": [ 1, 73, 196, 9, 174, 75, 185, 28, 31, 34, 34, 66, 84, 221, 121, 155, 0, 59, 78, 226, 150, 164, 253, 114, 150, 168, 89, 86, 12, 121, 241, 31, 141, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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