Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cedc644c6cc58fcbec74991504ebcf5ff035685fa192e28e7e509bd6c4809ff

Tx prefix hash: aaf3b82409a77408d33702f0fdf5f6611df95640f487846e16ab6a8730946e5e
Tx public key: 0c2fb73d0e9a8b289bcdf1e3c65df58028034d746bdee992d54f4b7bdfb01833
Timestamp: 1726173117 Timestamp [UCT]: 2024-09-12 20:31:57 Age [y:d:h:m:s]: 00:063:06:40:30
Block: 1108740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45219 RingCT/type: yes/0
Extra: 010c2fb73d0e9a8b289bcdf1e3c65df58028034d746bdee992d54f4b7bdfb0183302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc72d9ad08727758d7af2074996bc2ada238e9bfc5bc8fee0d30c4c33c1440d2 0.600000000000 1586741 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": 1108750, "vin": [ { "gen": { "height": 1108740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc72d9ad08727758d7af2074996bc2ada238e9bfc5bc8fee0d30c4c33c1440d2" } } ], "extra": [ 1, 12, 47, 183, 61, 14, 154, 139, 40, 155, 205, 241, 227, 198, 93, 245, 128, 40, 3, 77, 116, 107, 222, 233, 146, 213, 79, 75, 123, 223, 176, 24, 51, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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