Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c23c1624f368f3b1742900ab2b093ae16e455e06193196bd4849e63d23d414e

Tx prefix hash: 549e580b2d28a20f10ec0b9ac6798e35de4c5e5b9d835187310889442e790730
Tx public key: 1d66e462e1b7bd29ec2f706f49dd32f42956e10b793568285fda8dd6e82f3ef7
Timestamp: 1730515946 Timestamp [UCT]: 2024-11-02 02:52:26 Age [y:d:h:m:s]: 00:179:13:02:18
Block: 1144647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128171 RingCT/type: yes/0
Extra: 011d66e462e1b7bd29ec2f706f49dd32f42956e10b793568285fda8dd6e82f3ef7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e71a1a64222eb078bb1123262281906a4efbf44e4c2b3d95814ddc2a8bfa38 0.600000000000 1628918 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": 1144657, "vin": [ { "gen": { "height": 1144647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e71a1a64222eb078bb1123262281906a4efbf44e4c2b3d95814ddc2a8bfa38" } } ], "extra": [ 1, 29, 102, 228, 98, 225, 183, 189, 41, 236, 47, 112, 111, 73, 221, 50, 244, 41, 86, 225, 11, 121, 53, 104, 40, 95, 218, 141, 214, 232, 47, 62, 247, 2, 17, 0, 0, 0, 4, 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