Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3716e169ca61881a0f98e88aafa238488b6fc46112ad99c77e5ab8aed5e875ea

Tx prefix hash: 3f7ec8e78af7260b2ec4d853e7f4e2c5330641b99a0c5c762bb9404ef198a1f1
Tx public key: 0f2b068d1aa75752138fa486cc5128a45e40743b7ebbbbc599fa2e94f93fa29d
Timestamp: 1750793463 Timestamp [UCT]: 2025-06-24 19:31:03 Age [y:d:h:m:s]: 00:156:14:03:34
Block: 1312020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109864 RingCT/type: yes/0
Extra: 010f2b068d1aa75752138fa486cc5128a45e40743b7ebbbbc599fa2e94f93fa29d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae007a57d6b72cabffe142bc6b3701a1ad17838a226aaf685ad572c2f7f18a70 0.600000000000 1799651 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": 1312030, "vin": [ { "gen": { "height": 1312020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae007a57d6b72cabffe142bc6b3701a1ad17838a226aaf685ad572c2f7f18a70" } } ], "extra": [ 1, 15, 43, 6, 141, 26, 167, 87, 82, 19, 143, 164, 134, 204, 81, 40, 164, 94, 64, 116, 59, 126, 187, 187, 197, 153, 250, 46, 148, 249, 63, 162, 157, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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