Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8832ee0d237cb526336fd2ecd6ffb1d73851f771ef0b8e98acaabe4af924645

Tx prefix hash: 50fd45a29dbbbd284f1e438bef8d604c1c8e6c4b83b7faaba4a525fa6791be1f
Tx public key: 0ca2fc9ace1f501bd192f1ead6ccb3831f4ff29a5b6a4409a1d2483171735a9f
Timestamp: 1742832472 Timestamp [UCT]: 2025-03-24 16:07:52 Age [y:d:h:m:s]: 00:284:18:37:24
Block: 1246357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201345 RingCT/type: yes/0
Extra: 010ca2fc9ace1f501bd192f1ead6ccb3831f4ff29a5b6a4409a1d2483171735a9f021100000004c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc3d19b8fc751524c4ac26d63b4d1c1e0b8f3f17a1951bdc6b40f5c1f3098a32 0.600000000000 1733358 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": 1246367, "vin": [ { "gen": { "height": 1246357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc3d19b8fc751524c4ac26d63b4d1c1e0b8f3f17a1951bdc6b40f5c1f3098a32" } } ], "extra": [ 1, 12, 162, 252, 154, 206, 31, 80, 27, 209, 146, 241, 234, 214, 204, 179, 131, 31, 79, 242, 154, 91, 106, 68, 9, 161, 210, 72, 49, 113, 115, 90, 159, 2, 17, 0, 0, 0, 4, 198, 116, 9, 88, 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