Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f91ad5cf971f37b8bf00d1c9a0c9664a2aab3f1e30d7eaa030ad096f126ffb

Tx prefix hash: 2118d790a57bbc39d49def9a931297894fdba18c44cc92d96a6528bc1b3f0ee4
Tx public key: b71e4abe4da33e4ad7e0e54d17b122b5531fa801d7c4ee48b2726d29422ed0cc
Timestamp: 1739221131 Timestamp [UCT]: 2025-02-10 20:58:51 Age [y:d:h:m:s]: 00:326:16:45:32
Block: 1216477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231310 RingCT/type: yes/0
Extra: 01b71e4abe4da33e4ad7e0e54d17b122b5531fa801d7c4ee48b2726d29422ed0cc02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b7732717385292da339ca6dfa1647bd8390db8290b327bd731d6a6590ebdac 0.600000000000 1703282 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": 1216487, "vin": [ { "gen": { "height": 1216477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b7732717385292da339ca6dfa1647bd8390db8290b327bd731d6a6590ebdac" } } ], "extra": [ 1, 183, 30, 74, 190, 77, 163, 62, 74, 215, 224, 229, 77, 23, 177, 34, 181, 83, 31, 168, 1, 215, 196, 238, 72, 178, 114, 109, 41, 66, 46, 208, 204, 2, 17, 0, 0, 0, 15, 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