Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3480ab9570d0b2b9ecd10b498a0aa27d44b4c3b72b4f852ea3aa14777de3d5e

Tx prefix hash: 29a9579f67ed6db6283d54dd46f02708de609d1f01aad13679951cef135d3a4b
Tx public key: 0ef33fe1fe76c613f1bc9953ece23dd4f2e1e398aa116e47599385a5f5a0a837
Timestamp: 1726053958 Timestamp [UCT]: 2024-09-11 11:25:58 Age [y:d:h:m:s]: 01:053:13:39:29
Block: 1107752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296694 RingCT/type: yes/0
Extra: 010ef33fe1fe76c613f1bc9953ece23dd4f2e1e398aa116e47599385a5f5a0a837021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a573988f9499dc03f813f7ada3454cd994f56658882a71fbf43cb3730dc59a 0.600000000000 1585397 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": 1107762, "vin": [ { "gen": { "height": 1107752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a573988f9499dc03f813f7ada3454cd994f56658882a71fbf43cb3730dc59a" } } ], "extra": [ 1, 14, 243, 63, 225, 254, 118, 198, 19, 241, 188, 153, 83, 236, 226, 61, 212, 242, 225, 227, 152, 170, 17, 110, 71, 89, 147, 133, 165, 245, 160, 168, 55, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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