Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34079e1e7ec4ee26b0fa500c10e417e7a230783eeea55a77d97f6100d33df720

Tx prefix hash: af9bc99102228579c8a5dc7a2c5a2fe121d1f1a229cecac887c403c37565b049
Tx public key: c96752e90ad8de7b3d390624d22f3da95e307092b2b86290f179db407e6f5122
Timestamp: 1634277765 Timestamp [UCT]: 2021-10-15 06:02:45 Age [y:d:h:m:s]: 03:108:12:44:55
Block: 353381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855161 RingCT/type: yes/0
Extra: 01c96752e90ad8de7b3d390624d22f3da95e307092b2b86290f179db407e6f51220211000000255410958b000000000000000000

1 output(s) for total of 41.409736807000 dcy

stealth address amount amount idx
00: 0b245f8a6e02101cf1cb7e29ad6c53ce46cebbfd6d65c97dec96585440afb440 41.409736807000 722119 of 0

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": 353391, "vin": [ { "gen": { "height": 353381 } } ], "vout": [ { "amount": 41409736807, "target": { "key": "0b245f8a6e02101cf1cb7e29ad6c53ce46cebbfd6d65c97dec96585440afb440" } } ], "extra": [ 1, 201, 103, 82, 233, 10, 216, 222, 123, 61, 57, 6, 36, 210, 47, 61, 169, 94, 48, 112, 146, 178, 184, 98, 144, 241, 121, 219, 64, 126, 111, 81, 34, 2, 17, 0, 0, 0, 37, 84, 16, 149, 139, 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