Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1bf5affa962bdac666f80dac61a018f4faec482d46ad16271cfd75d8f0e217

Tx prefix hash: 331bb21cf0eee1a0e344bb0a4390ab3364936ea01eb59d1ec806d0a13e6fd4e3
Tx public key: 06dd5554d97369042b82d7478ef335ea585cf3e328c0ddcac764d28ac82f5b48
Timestamp: 1737290948 Timestamp [UCT]: 2025-01-19 12:49:08 Age [y:d:h:m:s]: 00:054:13:13:41
Block: 1200719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38813 RingCT/type: yes/0
Extra: 0106dd5554d97369042b82d7478ef335ea585cf3e328c0ddcac764d28ac82f5b48021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d64e20edc47581ba09e7685abc293a47bca7cf104d8fe93de5e54c205ab85e53 0.600000000000 1687364 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": 1200729, "vin": [ { "gen": { "height": 1200719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d64e20edc47581ba09e7685abc293a47bca7cf104d8fe93de5e54c205ab85e53" } } ], "extra": [ 1, 6, 221, 85, 84, 217, 115, 105, 4, 43, 130, 215, 71, 142, 243, 53, 234, 88, 92, 243, 227, 40, 192, 221, 202, 199, 100, 210, 138, 200, 47, 91, 72, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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