Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dfacf6779a4fd5d23a8e658333d5af8aae3e3eb6fd32295850d58cf6d24a721

Tx prefix hash: 16685e6d500a49ef779ed1180e9249df17c1cab821ecd9d95d9a97013e9459c9
Tx public key: ddf4c7a6b0260771fef5e2d69cd89d41e561b05ba9f2ebb953d7672ca6387936
Timestamp: 1732858622 Timestamp [UCT]: 2024-11-29 05:37:02 Age [y:d:h:m:s]: 00:206:09:18:43
Block: 1164061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147133 RingCT/type: yes/0
Extra: 01ddf4c7a6b0260771fef5e2d69cd89d41e561b05ba9f2ebb953d7672ca63879360211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f74ee4fc25aedcd529eaa55d7ae85152c8c4f1fe6f1421983d82821062ba859 0.600000000000 1649732 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": 1164071, "vin": [ { "gen": { "height": 1164061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f74ee4fc25aedcd529eaa55d7ae85152c8c4f1fe6f1421983d82821062ba859" } } ], "extra": [ 1, 221, 244, 199, 166, 176, 38, 7, 113, 254, 245, 226, 214, 156, 216, 157, 65, 229, 97, 176, 91, 169, 242, 235, 185, 83, 215, 103, 44, 166, 56, 121, 54, 2, 17, 0, 0, 0, 2, 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